Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 901a4de5f4c3ce3522cc7b0472f437b8dfd3017b0e63909cd2fed4b1f90492c2

Tx prefix hash: a4e421387917e8eee707e0200579c8ddac19b993430d40f0683f9b8ca7289a26
Tx public key: 8abd020dd7abcd43f185fc382714f97abd1b81cdd2c2e81703240518d9615028
Timestamp: 1580889156 Timestamp [UCT]: 2020-02-05 07:52:36 Age [y:d:h:m:s]: 04:286:04:58:40
Block: 59108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1095873 RingCT/type: yes/0
Extra: 018abd020dd7abcd43f185fc382714f97abd1b81cdd2c2e81703240518d961502802110000000149b77a3d000000000000000000

1 output(s) for total of 390.992572016000 dcy

stealth address amount amount idx
00: 88d5f4ad2703a9a37300db1ea17988849d58dd841ac62f91f1ef11df7baf580b 390.992572016000 109111 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": 59118, "vin": [ { "gen": { "height": 59108 } } ], "vout": [ { "amount": 390992572016, "target": { "key": "88d5f4ad2703a9a37300db1ea17988849d58dd841ac62f91f1ef11df7baf580b" } } ], "extra": [ 1, 138, 189, 2, 13, 215, 171, 205, 67, 241, 133, 252, 56, 39, 20, 249, 122, 189, 27, 129, 205, 210, 194, 232, 23, 3, 36, 5, 24, 217, 97, 80, 40, 2, 17, 0, 0, 0, 1, 73, 183, 122, 61, 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