Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d921b8bd0ccd03011ce322280d95d792ad19947bd797d75fb2dbcd7ff0f15d3

Tx prefix hash: fb6c50cf4f6ec34faf606e94f7836ccd313ee16c3502a2757b1e5b2ac4b18ec5
Tx public key: 764ce1e3e1f00d5acdae00872ac9322cd284826d9609f2d2c7aa8effa42c66f3
Timestamp: 1751070020 Timestamp [UCT]: 2025-06-28 00:20:20 Age [y:d:h:m:s]: 00:141:04:10:45
Block: 1314151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98988 RingCT/type: yes/0
Extra: 01764ce1e3e1f00d5acdae00872ac9322cd284826d9609f2d2c7aa8effa42c66f30211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c67f88b46c8bc90ef19e80f19a58e8b0b7fdce3770d23e58ade55fedec435883 0.600000000000 1801796 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": 1314161, "vin": [ { "gen": { "height": 1314151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c67f88b46c8bc90ef19e80f19a58e8b0b7fdce3770d23e58ade55fedec435883" } } ], "extra": [ 1, 118, 76, 225, 227, 225, 240, 13, 90, 205, 174, 0, 135, 42, 201, 50, 44, 210, 132, 130, 109, 150, 9, 242, 210, 199, 170, 142, 255, 164, 44, 102, 243, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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