Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 1b222beaf9dbd163e9a46503a276e5f2ac27c4730768c499e1d3c89231e74b7e

Tx prefix hash: 3dfed41a2f03da252a3f3c5c1cc0bc044c1e06d81df20f7a33f197a6bb5d81c7
Tx public key: f72311042800931440924be46a2e68cf2b89bed0bef34ab8045b5a6eaa82e973
Timestamp: 1719257506 Timestamp [UCT]: 2024-06-24 19:31:46 Age [y:d:h:m:s]: 00:121:06:44:40
Block: 1051388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86853 RingCT/type: yes/0
Extra: 01f72311042800931440924be46a2e68cf2b89bed0bef34ab8045b5a6eaa82e973021100000004a6fba9af000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fd401fb522d906bc2c5a6f413d3b1ca31d400d2f36729a6c4a23d59f007e904 0.600000000000 1521699 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1051398, "vin": [ { "gen": { "height": 1051388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fd401fb522d906bc2c5a6f413d3b1ca31d400d2f36729a6c4a23d59f007e904" } } ], "extra": [ 1, 247, 35, 17, 4, 40, 0, 147, 20, 64, 146, 75, 228, 106, 46, 104, 207, 43, 137, 190, 208, 190, 243, 74, 184, 4, 91, 90, 110, 170, 130, 233, 115, 2, 17, 0, 0, 0, 4, 166, 251, 169, 175, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8