Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6791b48e955643121378b59eb768e0b586a1b2beb71c15fbac7a44bd6af38d27

Tx prefix hash: 72f442d366e9aa2a8ea343c8c8a02c7f6894f815410814359dcee25ecbe5b7ad
Tx public key: a23fc1fb1c3228617712f2db70993ab45c9fb6eb29d00e8c67b95f02ee7a60b4
Timestamp: 1699511094 Timestamp [UCT]: 2023-11-09 06:24:54 Age [y:d:h:m:s]: 01:178:00:20:06
Block: 887697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388431 RingCT/type: yes/0
Extra: 01a23fc1fb1c3228617712f2db70993ab45c9fb6eb29d00e8c67b95f02ee7a60b402110000000e4b8f5122000000000000000000

1 output(s) for total of 0.702572812000 dcy

stealth address amount amount idx
00: 7efc9a983d29f63bf1b7d4df0fa75238b3ac570162db7f0d1ce99f11e0b46c56 0.702572812000 1343590 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": 887707, "vin": [ { "gen": { "height": 887697 } } ], "vout": [ { "amount": 702572812, "target": { "key": "7efc9a983d29f63bf1b7d4df0fa75238b3ac570162db7f0d1ce99f11e0b46c56" } } ], "extra": [ 1, 162, 63, 193, 251, 28, 50, 40, 97, 119, 18, 242, 219, 112, 153, 58, 180, 92, 159, 182, 235, 41, 208, 14, 140, 103, 185, 95, 2, 238, 122, 96, 180, 2, 17, 0, 0, 0, 14, 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