Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 829d71c2ca77c59d2d4fd59f853f2c285888f02fe7a93058b23c0b78c392facd

Tx prefix hash: ef419275e93b9840786d7a32fad133d6c60373ee41e393f400e8aa1be71b344a
Tx public key: f60fc24e2f284c66c2519a0ef5b1b4596a1dafd12e19748a43195590e56c0bdf
Timestamp: 1753328816 Timestamp [UCT]: 2025-07-24 03:46:56 Age [y:d:h:m:s]: 00:105:21:56:33
Block: 1332103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74499 RingCT/type: yes/0
Extra: 01f60fc24e2f284c66c2519a0ef5b1b4596a1dafd12e19748a43195590e56c0bdf021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ab1cfac557d983831215f4d4acca2b1b41148caf2d7f4404567de3328c5b417 0.600000000000 1819900 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": 1332113, "vin": [ { "gen": { "height": 1332103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ab1cfac557d983831215f4d4acca2b1b41148caf2d7f4404567de3328c5b417" } } ], "extra": [ 1, 246, 15, 194, 78, 47, 40, 76, 102, 194, 81, 154, 14, 245, 177, 180, 89, 106, 29, 175, 209, 46, 25, 116, 138, 67, 25, 85, 144, 229, 108, 11, 223, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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