Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 891089a682a9682ffcf90c8287fcc16b2f86d4c3a57aa05efcbe84de44b3ab6a

Tx prefix hash: 366c191c11024c6c31d55303a16f953b6c90234dd41ddfb8be4872f2ef487fac
Tx public key: 80c864f2772b582c3e73c9ecb30b5057b09f806db3473f475ebeedb1aedf50c8
Timestamp: 1697284824 Timestamp [UCT]: 2023-10-14 12:00:24 Age [y:d:h:m:s]: 01:178:21:11:53
Block: 869443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388872 RingCT/type: yes/0
Extra: 0180c864f2772b582c3e73c9ecb30b5057b09f806db3473f475ebeedb1aedf50c80211000000014b8f5122000000000000000000

1 output(s) for total of 0.807559343000 dcy

stealth address amount amount idx
00: dd7efcd70fffab529c2c39a121fd648e709a357c9568168bb1680fb7ab82d890 0.807559343000 1324288 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": 869453, "vin": [ { "gen": { "height": 869443 } } ], "vout": [ { "amount": 807559343, "target": { "key": "dd7efcd70fffab529c2c39a121fd648e709a357c9568168bb1680fb7ab82d890" } } ], "extra": [ 1, 128, 200, 100, 242, 119, 43, 88, 44, 62, 115, 201, 236, 179, 11, 80, 87, 176, 159, 128, 109, 179, 71, 63, 71, 94, 190, 237, 177, 174, 223, 80, 200, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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