Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 441f6c64749c2ddcbecf4e61d3878dd85dbb5f806e6377660eaf23b5d2a8399a

Tx prefix hash: d07a8e25ba4f45f2aadc9e35d2c1b340eef04e0bd3225d22daf7acbfe92592b8
Tx public key: 3ab3646525cf21c04c08c9d8202ee5eec4068afc515cbf5e6d006a853c6c3ded
Timestamp: 1751618084 Timestamp [UCT]: 2025-07-04 08:34:44 Age [y:d:h:m:s]: 00:133:12:05:39
Block: 1318500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93693 RingCT/type: yes/0
Extra: 013ab3646525cf21c04c08c9d8202ee5eec4068afc515cbf5e6d006a853c6c3ded02110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e864cdbf60711807d39ae3122b1653bee3fe6325e9090b4e77bfd38b98c6cbd 0.600000000000 1806181 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": 1318510, "vin": [ { "gen": { "height": 1318500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e864cdbf60711807d39ae3122b1653bee3fe6325e9090b4e77bfd38b98c6cbd" } } ], "extra": [ 1, 58, 179, 100, 101, 37, 207, 33, 192, 76, 8, 201, 216, 32, 46, 229, 238, 196, 6, 138, 252, 81, 92, 191, 94, 109, 0, 106, 133, 60, 108, 61, 237, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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