Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf3e33adbb27d0e9a440123a51c8efad691d6a3985e4f898d2987c26ae4ddbb0

Tx prefix hash: e875fd152c696e8ae15950fa1e704a68f546d9ae6690507e585891b160f49cad
Tx public key: b22b49a464e51f9950eea4945bd209c33ec301f5ae03288a874dc608ab73881d
Timestamp: 1718146995 Timestamp [UCT]: 2024-06-11 23:03:15 Age [y:d:h:m:s]: 00:133:10:30:54
Block: 1042203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95540 RingCT/type: yes/0
Extra: 01b22b49a464e51f9950eea4945bd209c33ec301f5ae03288a874dc608ab73881d0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b230de2823115e65aedf471cf455a1808ee7822664feb0d4c9b0c719fb0d6e6 0.600000000000 1511062 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": 1042213, "vin": [ { "gen": { "height": 1042203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b230de2823115e65aedf471cf455a1808ee7822664feb0d4c9b0c719fb0d6e6" } } ], "extra": [ 1, 178, 43, 73, 164, 100, 229, 31, 153, 80, 238, 164, 148, 91, 210, 9, 195, 62, 195, 1, 245, 174, 3, 40, 138, 135, 77, 198, 8, 171, 115, 136, 29, 2, 17, 0, 0, 0, 4, 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