Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dddd5d5483d84ad446efd069582ec266254bde7ff02e7c0e6eceb3b95f80a572

Tx prefix hash: 966f5373d1decedecca4c9c3268ca832997342336c1d5bb88ead60d3d93c7b9e
Tx public key: 75f20ebd48258f3592601b827ed78f2dfb5a83d92e2bf54f5d91395240a970f9
Timestamp: 1713180983 Timestamp [UCT]: 2024-04-15 11:36:23 Age [y:d:h:m:s]: 01:042:07:03:21
Block: 1001013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291212 RingCT/type: yes/0
Extra: 0175f20ebd48258f3592601b827ed78f2dfb5a83d92e2bf54f5d91395240a970f90211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4d176b854cacf00e366c87b41f8b097e57354b5098340dd022d579a359bdbe5 0.600000000000 1461515 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": 1001023, "vin": [ { "gen": { "height": 1001013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4d176b854cacf00e366c87b41f8b097e57354b5098340dd022d579a359bdbe5" } } ], "extra": [ 1, 117, 242, 14, 189, 72, 37, 143, 53, 146, 96, 27, 130, 126, 215, 143, 45, 251, 90, 131, 217, 46, 43, 245, 79, 93, 145, 57, 82, 64, 169, 112, 249, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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