Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b0d5ffc177194f645263bbb427a2a39f087a81f6eb22fb16e396e4d07b48ede

Tx prefix hash: 30841dfc55976e592858d4b512087727819e840a102c678dca4b3b439008196f
Tx public key: 0cee2235eb34c3a53033ee49ee61fd63274201a2d97c969d0c74a9027dd4b063
Timestamp: 1722622696 Timestamp [UCT]: 2024-08-02 18:18:16 Age [y:d:h:m:s]: 00:246:00:58:23
Block: 1079295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175741 RingCT/type: yes/0
Extra: 010cee2235eb34c3a53033ee49ee61fd63274201a2d97c969d0c74a9027dd4b06302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c95ac53a1592c272b5cb132d3cba46d561d6c0fbdcbc9a755592b6c7414a64c 0.600000000000 1552188 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": 1079305, "vin": [ { "gen": { "height": 1079295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c95ac53a1592c272b5cb132d3cba46d561d6c0fbdcbc9a755592b6c7414a64c" } } ], "extra": [ 1, 12, 238, 34, 53, 235, 52, 195, 165, 48, 51, 238, 73, 238, 97, 253, 99, 39, 66, 1, 162, 217, 124, 150, 157, 12, 116, 169, 2, 125, 212, 176, 99, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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