Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccba32de4105f13ffe6fbbb260053ea2a4e4e18243cc725a3409e5f8de5a3571

Tx prefix hash: 74a895937564568c61658b331538cae1c132becea67d282e78fb81205a6c36c7
Tx public key: 5d81ddd47f00d1325a624eba8eaf80e6e7ac59951a6bc8ffaae3e447fd03659f
Timestamp: 1696100808 Timestamp [UCT]: 2023-09-30 19:06:48 Age [y:d:h:m:s]: 01:200:10:41:38
Block: 859622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404316 RingCT/type: yes/0
Extra: 015d81ddd47f00d1325a624eba8eaf80e6e7ac59951a6bc8ffaae3e447fd03659f021100000003faf35c9c000000000000000000

1 output(s) for total of 0.870393242000 dcy

stealth address amount amount idx
00: af8cc3b5bdb7625c3696ccb9d3d76f0b1d970421cc2ee291826e9b05221abf11 0.870393242000 1313856 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": 859632, "vin": [ { "gen": { "height": 859622 } } ], "vout": [ { "amount": 870393242, "target": { "key": "af8cc3b5bdb7625c3696ccb9d3d76f0b1d970421cc2ee291826e9b05221abf11" } } ], "extra": [ 1, 93, 129, 221, 212, 127, 0, 209, 50, 90, 98, 78, 186, 142, 175, 128, 230, 231, 172, 89, 149, 26, 107, 200, 255, 170, 227, 228, 71, 253, 3, 101, 159, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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