Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db0086bbec9323d6fd52486e0efb1034e956346b6d463040cf4589a70b6cbe47

Tx prefix hash: e7a1a5f1ca98bd7e652c0de148804896f392033721af2c455a6107262f505fd8
Tx public key: 3968c9b15debb7bbc91fb166a2b9f5be9a85c5fe6dddcf45ccbfd354f29b0ad3
Timestamp: 1750921804 Timestamp [UCT]: 2025-06-26 07:10:04 Age [y:d:h:m:s]: 00:147:00:51:25
Block: 1313028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103078 RingCT/type: yes/0
Extra: 013968c9b15debb7bbc91fb166a2b9f5be9a85c5fe6dddcf45ccbfd354f29b0ad30211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc334c82644b993a1799780630413ede7a664d0da5eb95028e4d551a27d534d6 0.600000000000 1800665 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": 1313038, "vin": [ { "gen": { "height": 1313028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc334c82644b993a1799780630413ede7a664d0da5eb95028e4d551a27d534d6" } } ], "extra": [ 1, 57, 104, 201, 177, 93, 235, 183, 187, 201, 31, 177, 102, 162, 185, 245, 190, 154, 133, 197, 254, 109, 221, 207, 69, 204, 191, 211, 84, 242, 155, 10, 211, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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