Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc9b04821038f0e29a8f9985d90177ea082b226b9cdcc87c940ad08a2b20639e

Tx prefix hash: 16d4141ed78a4175ef0e2b2a2d271dd91730244f2a7bf91403d1a07e12cb2700
Tx public key: bee8dce57250b5696c97f6115b04873112488c55ccc264f76797c625ab50c0b8
Timestamp: 1705438273 Timestamp [UCT]: 2024-01-16 20:51:13 Age [y:d:h:m:s]: 01:060:15:25:13
Block: 936818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304447 RingCT/type: yes/0
Extra: 01bee8dce57250b5696c97f6115b04873112488c55ccc264f76797c625ab50c0b80211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba1bfcb2184608320d2f2f4c21481ab7d311340d3ba7363b34f28858e21b2dd1 0.600000000000 1394858 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": 936828, "vin": [ { "gen": { "height": 936818 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba1bfcb2184608320d2f2f4c21481ab7d311340d3ba7363b34f28858e21b2dd1" } } ], "extra": [ 1, 190, 232, 220, 229, 114, 80, 181, 105, 108, 151, 246, 17, 91, 4, 135, 49, 18, 72, 140, 85, 204, 194, 100, 247, 103, 151, 198, 37, 171, 80, 192, 184, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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