Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0bdda7339d69c230dbe5052ba313b8a1d053fc57e3e873dd37ae5469be7e565

Tx prefix hash: d037529920f063e26016ec174dc5e61709a74f78a2435fecca5515dcbc1dd45a
Tx public key: 8a91a0c398ba407914bfdc1e06ca577d4cb7a13955bc509ecabe2efc7cbe52fd
Timestamp: 1708698109 Timestamp [UCT]: 2024-02-23 14:21:49 Age [y:d:h:m:s]: 01:023:23:14:45
Block: 963861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278157 RingCT/type: yes/0
Extra: 018a91a0c398ba407914bfdc1e06ca577d4cb7a13955bc509ecabe2efc7cbe52fd0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83f0ba47d8025b1a372efab3552c6261a8c1329496f65e0e071da6a4782815cd 0.600000000000 1423588 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": 963871, "vin": [ { "gen": { "height": 963861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83f0ba47d8025b1a372efab3552c6261a8c1329496f65e0e071da6a4782815cd" } } ], "extra": [ 1, 138, 145, 160, 195, 152, 186, 64, 121, 20, 191, 220, 30, 6, 202, 87, 125, 76, 183, 161, 57, 85, 188, 80, 158, 202, 190, 46, 252, 124, 190, 82, 253, 2, 17, 0, 0, 0, 3, 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