Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 147f1cbab53cf5196c408716ea94d7a889776d3798bfe227d680ad06179cfbbf

Tx prefix hash: 4b6742ff8056a7b4fd066f293ff69ead3a3fd25d6571dee9c15ee4b4d5c17fd7
Tx public key: 8af055279643b636cea2b89fb5ab4bd1ab5dc3eb56b783d95fc2ea8164ee997d
Timestamp: 1741815245 Timestamp [UCT]: 2025-03-12 21:34:05 Age [y:d:h:m:s]: 00:324:20:28:10
Block: 1237954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229821 RingCT/type: yes/0
Extra: 018af055279643b636cea2b89fb5ab4bd1ab5dc3eb56b783d95fc2ea8164ee997d02110000000e007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae7fb8eadde889e197ac5aa0020f869d3b03563420c04cba9280a578f19265c5 0.600000000000 1724913 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": 1237964, "vin": [ { "gen": { "height": 1237954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae7fb8eadde889e197ac5aa0020f869d3b03563420c04cba9280a578f19265c5" } } ], "extra": [ 1, 138, 240, 85, 39, 150, 67, 182, 54, 206, 162, 184, 159, 181, 171, 75, 209, 171, 93, 195, 235, 86, 183, 131, 217, 95, 194, 234, 129, 100, 238, 153, 125, 2, 17, 0, 0, 0, 14, 0, 127, 151, 138, 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