Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0262f8a9504ebe53cb6d11bc5999072e29fa3b3116e8111889eef59c40b55c85

Tx prefix hash: cc9cccbd85a233c35ae7f31c04f2b724c32664d2278cdb16666b9a38ed6099a2
Tx public key: ac93423cc1e7138cc97de0fb892cc66806c5820f461af064c7ae17e2436c20af
Timestamp: 1697384437 Timestamp [UCT]: 2023-10-15 15:40:37 Age [y:d:h:m:s]: 01:184:20:00:00
Block: 870270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393127 RingCT/type: yes/0
Extra: 01ac93423cc1e7138cc97de0fb892cc66806c5820f461af064c7ae17e2436c20af0211000000024b8f5122000000000000000000

1 output(s) for total of 0.802480061000 dcy

stealth address amount amount idx
00: b52163677d0d0461097552f430e5d44f0b14ad05648f12f951b8f5c02d3555e3 0.802480061000 1325149 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": 870280, "vin": [ { "gen": { "height": 870270 } } ], "vout": [ { "amount": 802480061, "target": { "key": "b52163677d0d0461097552f430e5d44f0b14ad05648f12f951b8f5c02d3555e3" } } ], "extra": [ 1, 172, 147, 66, 60, 193, 231, 19, 140, 201, 125, 224, 251, 137, 44, 198, 104, 6, 197, 130, 15, 70, 26, 240, 100, 199, 174, 23, 226, 67, 108, 32, 175, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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