Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 185687f9bed48f08f569fa42c9943a11a33724a20cdb3f3703d3b48178f83fe3

Tx prefix hash: 4e8e4c87019ece7f17c5c34e6fadf090695727a99317118393d12f28e53b425e
Tx public key: 0d8b8d8e1ba61e0dc8a5ae0d829ce47bf2db85488f995ed532cdd6e1b630d630
Timestamp: 1705159779 Timestamp [UCT]: 2024-01-13 15:29:39 Age [y:d:h:m:s]: 01:065:20:10:28
Block: 934507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308169 RingCT/type: yes/0
Extra: 010d8b8d8e1ba61e0dc8a5ae0d829ce47bf2db85488f995ed532cdd6e1b630d6300211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1a7ac08543d5115cc00baa05e9b1176831e3155c4fdcff59cad3c0aa52dfb75 0.600000000000 1392521 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": 934517, "vin": [ { "gen": { "height": 934507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1a7ac08543d5115cc00baa05e9b1176831e3155c4fdcff59cad3c0aa52dfb75" } } ], "extra": [ 1, 13, 139, 141, 142, 27, 166, 30, 13, 200, 165, 174, 13, 130, 156, 228, 123, 242, 219, 133, 72, 143, 153, 94, 213, 50, 205, 214, 225, 182, 48, 214, 48, 2, 17, 0, 0, 0, 2, 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