Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c72148e725b243dc32ff8d55d7b915de582198910f45aaea8d02fa038ee40d46

Tx prefix hash: de9e0b8aef76ab0ea48c6cd0cc5f60c5fa1a21af76a8c582285f53deacb8f59b
Tx public key: 4edf4fc4b9e4f6177ed4a5e81a173a458e23693e06936b1ecd1dfc138218f63f
Timestamp: 1741416034 Timestamp [UCT]: 2025-03-08 06:40:34 Age [y:d:h:m:s]: 00:247:13:05:08
Block: 1234638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174659 RingCT/type: yes/0
Extra: 014edf4fc4b9e4f6177ed4a5e81a173a458e23693e06936b1ecd1dfc138218f63f0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600150000000 dcy

stealth address amount amount idx
00: b2c5dab607fa14886d4eca03ee15b3c08ec020dcd954a4f5ecf9fff46392fcc9 0.600150000000 1721569 of 0

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": 1234648, "vin": [ { "gen": { "height": 1234638 } } ], "vout": [ { "amount": 600150000, "target": { "key": "b2c5dab607fa14886d4eca03ee15b3c08ec020dcd954a4f5ecf9fff46392fcc9" } } ], "extra": [ 1, 78, 223, 79, 196, 185, 228, 246, 23, 126, 212, 165, 232, 26, 23, 58, 69, 142, 35, 105, 62, 6, 147, 107, 30, 205, 29, 252, 19, 130, 24, 246, 63, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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