Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 361b3bc6f02fc9f01832a4a1d9568f8dde95e417af7dc5b633b3766b2153eca2

Tx prefix hash: 2e653ff0ab92b8dfcb847257f2df2389b6dba9d6c5bf8e08aa2f85540923872d
Tx public key: aad0cbe7bb15fb30f981e7a956af2aaee3cfe2bf05b271ade9dbe49a950f8ab2
Timestamp: 1635581858 Timestamp [UCT]: 2021-10-30 08:17:38 Age [y:d:h:m:s]: 03:230:19:53:31
Block: 363507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 943195 RingCT/type: yes/0
Extra: 01aad0cbe7bb15fb30f981e7a956af2aaee3cfe2bf05b271ade9dbe49a950f8ab2021100000005a272b9cb000000000000000000

1 output(s) for total of 38.331728636000 dcy

stealth address amount amount idx
00: 833dce4ffddabbf028c6b2f98d31523aa6296ed2512e5f063ca710feb2b0941f 38.331728636000 738783 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": 363517, "vin": [ { "gen": { "height": 363507 } } ], "vout": [ { "amount": 38331728636, "target": { "key": "833dce4ffddabbf028c6b2f98d31523aa6296ed2512e5f063ca710feb2b0941f" } } ], "extra": [ 1, 170, 208, 203, 231, 187, 21, 251, 48, 249, 129, 231, 169, 86, 175, 42, 174, 227, 207, 226, 191, 5, 178, 113, 173, 233, 219, 228, 154, 149, 15, 138, 178, 2, 17, 0, 0, 0, 5, 162, 114, 185, 203, 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