Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09e937eb0d29ca5c235efab52fa6780003dd41625716bfcf92b5ee626d5703ab

Tx prefix hash: cf86077a410483a4e7427ca8f9e13fb357c710c648e4737d0f323b5e5e4ed835
Tx public key: f90ab043595c9405609c1f34dfec40dec78fa99f9a6e878a4df617fca187c6ce
Timestamp: 1574718425 Timestamp [UCT]: 2019-11-25 21:47:05 Age [y:d:h:m:s]: 05:160:17:01:31
Block: 17447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1257486 RingCT/type: yes/0
Extra: 01f90ab043595c9405609c1f34dfec40dec78fa99f9a6e878a4df617fca187c6ce021100000001f95225a5000000000000000000

1 output(s) for total of 537.281300890000 dcy

stealth address amount amount idx
00: af2c1c37f0fcf5d2bbdacf4dc22db490f49e04c1add33c30023a34e85fb99609 537.281300890000 25379 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": 17457, "vin": [ { "gen": { "height": 17447 } } ], "vout": [ { "amount": 537281300890, "target": { "key": "af2c1c37f0fcf5d2bbdacf4dc22db490f49e04c1add33c30023a34e85fb99609" } } ], "extra": [ 1, 249, 10, 176, 67, 89, 92, 148, 5, 96, 156, 31, 52, 223, 236, 64, 222, 199, 143, 169, 159, 154, 110, 135, 138, 77, 246, 23, 252, 161, 135, 198, 206, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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