Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5b26539725a02cb147058ff0f3a03e959ef7e2127885e18a6cfd6c0cebc72c9

Tx prefix hash: 539441c68d2ded299a9a6a12f1f51085fb4a14e7f376600d05b9afff945620e2
Tx public key: f3bfb39371799ca04fce1c6ca84c35cb8ee988e71b333080945599d7898150c2
Timestamp: 1710564549 Timestamp [UCT]: 2024-03-16 04:49:09 Age [y:d:h:m:s]: 01:244:23:41:56
Block: 979347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433792 RingCT/type: yes/0
Extra: 01f3bfb39371799ca04fce1c6ca84c35cb8ee988e71b333080945599d7898150c202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e9d6aa3f51db10baf3c5e9813e60bdb99e9dd5fcc1effdbd970d96856ef3dcb 0.600000000000 1439380 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": 979357, "vin": [ { "gen": { "height": 979347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e9d6aa3f51db10baf3c5e9813e60bdb99e9dd5fcc1effdbd970d96856ef3dcb" } } ], "extra": [ 1, 243, 191, 179, 147, 113, 121, 156, 160, 79, 206, 28, 108, 168, 76, 53, 203, 142, 233, 136, 231, 27, 51, 48, 128, 148, 85, 153, 215, 137, 129, 80, 194, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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