Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1808ac5b332a03271c4841897704066791fc1e5cad5a92e2fe766e8261693eac

Tx prefix hash: e9b263f7a76211d161585bc6f26a768dce1ad3a08acbe5fe9b7ac46155932386
Tx public key: 3514b71c099833a907fa2ad752d123f588ea1d0cfc8ea6f338f4e9c5359e0889
Timestamp: 1684745719 Timestamp [UCT]: 2023-05-22 08:55:19 Age [y:d:h:m:s]: 01:317:12:08:27
Block: 765537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488121 RingCT/type: yes/0
Extra: 013514b71c099833a907fa2ad752d123f588ea1d0cfc8ea6f338f4e9c5359e088902110000000733af99f4000000000000000000

1 output(s) for total of 1.784260700000 dcy

stealth address amount amount idx
00: c9dc360d37c2b524c7e78c315402d739baea357e3e2fe0658aefeafc906daa3d 1.784260700000 1214530 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": 765547, "vin": [ { "gen": { "height": 765537 } } ], "vout": [ { "amount": 1784260700, "target": { "key": "c9dc360d37c2b524c7e78c315402d739baea357e3e2fe0658aefeafc906daa3d" } } ], "extra": [ 1, 53, 20, 183, 28, 9, 152, 51, 169, 7, 250, 42, 215, 82, 209, 35, 245, 136, 234, 29, 12, 252, 142, 166, 243, 56, 244, 233, 197, 53, 158, 8, 137, 2, 17, 0, 0, 0, 7, 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