Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d835153ba1933f61b373e3f8a05912e015b53cd7b613f2df95f851e55a55689c

Tx prefix hash: 34ef5d478a3f79880c3f2476190b51c4e4fc0eabdd2e8e6293138d1bc55be1c6
Tx public key: ae922bf19eca44d8932e216bd0dc4c1b58e7cb18c7a379015b05378b2cfa2121
Timestamp: 1577120806 Timestamp [UCT]: 2019-12-23 17:06:46 Age [y:d:h:m:s]: 05:011:01:58:44
Block: 30037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1158029 RingCT/type: yes/0
Extra: 01ae922bf19eca44d8932e216bd0dc4c1b58e7cb18c7a379015b05378b2cfa21210211000000224943cd9f000000000000000000

1 output(s) for total of 488.062918175000 dcy

stealth address amount amount idx
00: 926a4876d760537a8cb4f99b0d789f8d5fe45c60fd8807aedcdb5357576426dc 488.062918175000 49587 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": 30047, "vin": [ { "gen": { "height": 30037 } } ], "vout": [ { "amount": 488062918175, "target": { "key": "926a4876d760537a8cb4f99b0d789f8d5fe45c60fd8807aedcdb5357576426dc" } } ], "extra": [ 1, 174, 146, 43, 241, 158, 202, 68, 216, 147, 46, 33, 107, 208, 220, 76, 27, 88, 231, 203, 24, 199, 163, 121, 1, 91, 5, 55, 139, 44, 250, 33, 33, 2, 17, 0, 0, 0, 34, 73, 67, 205, 159, 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