Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f71114b62cf32858ed03e83a33154fac60e2fb27cd6c294bc7b7e67f993c2e2d

Tx prefix hash: 96fc974f3d4dc8e33d5a8de2f85a85d838f66d6f6003114562e02614a79ac2ff
Tx public key: 6614ddeb76e4e4b58bbc439b66537bdf4395addcdf56371408b4820b8fbedaf6
Timestamp: 1696567750 Timestamp [UCT]: 2023-10-06 04:49:10 Age [y:d:h:m:s]: 01:193:23:10:21
Block: 863490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399676 RingCT/type: yes/0
Extra: 016614ddeb76e4e4b58bbc439b66537bdf4395addcdf56371408b4820b8fbedaf602110000000233af99f4000000000000000000

1 output(s) for total of 0.845082708000 dcy

stealth address amount amount idx
00: 61a2a453e9f5347c0c773e89c939ebbf1c6db08677308e251c30dea2be2348b0 0.845082708000 1317946 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": 863500, "vin": [ { "gen": { "height": 863490 } } ], "vout": [ { "amount": 845082708, "target": { "key": "61a2a453e9f5347c0c773e89c939ebbf1c6db08677308e251c30dea2be2348b0" } } ], "extra": [ 1, 102, 20, 221, 235, 118, 228, 228, 181, 139, 188, 67, 155, 102, 83, 123, 223, 67, 149, 173, 220, 223, 86, 55, 20, 8, 180, 130, 11, 143, 190, 218, 246, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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