Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 630dc36c0c1a4f5ab55e569fafd682f87ab439513f3e0221ca5efebcf6f4f5c7

Tx prefix hash: a33e51565f179a1cd7605d13fe5164b541517e37298aaa63dcdb233c287025ec
Tx public key: 0293e2ca143dcfbf54b4014fdca8c8de55a554f90cfdf9432695d9ae5a3a7cb4
Timestamp: 1578818482 Timestamp [UCT]: 2020-01-12 08:41:22 Age [y:d:h:m:s]: 04:352:15:58:50
Block: 43785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1141580 RingCT/type: yes/0
Extra: 010293e2ca143dcfbf54b4014fdca8c8de55a554f90cfdf9432695d9ae5a3a7cb40211000000c5391a8d0e000000000000000000

1 output(s) for total of 439.471242641000 dcy

stealth address amount amount idx
00: dc1c153526e6b9a6de5e6b7e052fce6de32825b370c2c60b77a70330226c5911 439.471242641000 79425 of 0

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": 43795, "vin": [ { "gen": { "height": 43785 } } ], "vout": [ { "amount": 439471242641, "target": { "key": "dc1c153526e6b9a6de5e6b7e052fce6de32825b370c2c60b77a70330226c5911" } } ], "extra": [ 1, 2, 147, 226, 202, 20, 61, 207, 191, 84, 180, 1, 79, 220, 168, 200, 222, 85, 165, 84, 249, 12, 253, 249, 67, 38, 149, 217, 174, 90, 58, 124, 180, 2, 17, 0, 0, 0, 197, 57, 26, 141, 14, 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