Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58360a2dbe6b43ad2c59c10182b7ade3795cfe6bb3c6e44c88a0f6087b72a803

Tx prefix hash: bb26b65569d807de7233d0830586728eaef29d9f8fdd2402d314d51b4761e1f2
Tx public key: 76a520f26df114d6bddbeb3f3016476fc64ef8211e85c19e9aea21a4666d9c78
Timestamp: 1764328942 Timestamp [UCT]: 2025-11-28 11:22:22 Age [y:d:h:m:s]: 00:065:01:26:59
Block: 1421936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46398 RingCT/type: yes/0
Extra: 0176a520f26df114d6bddbeb3f3016476fc64ef8211e85c19e9aea21a4666d9c78021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1596314f41bb5bb064bd7d38a5229bddc26951eaf8846b39117f5e8317ffa910 0.600000000000 1910499 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": 1421946, "vin": [ { "gen": { "height": 1421936 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1596314f41bb5bb064bd7d38a5229bddc26951eaf8846b39117f5e8317ffa910" } } ], "extra": [ 1, 118, 165, 32, 242, 109, 241, 20, 214, 189, 219, 235, 63, 48, 22, 71, 111, 198, 78, 248, 33, 30, 133, 193, 158, 154, 234, 33, 164, 102, 109, 156, 120, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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