Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6403573f24169007777f1aa5ad2a116db0079e57ac8c1ae644bed75d3c3c447e

Tx prefix hash: 3578068e569a907d925983ebe101c375e058033f416fc1c16980e0d0925858f6
Tx public key: c0d9e458a2d4e48ae0cdf274cda45e1468f661ef9fcc858e707c50f7040beab5
Timestamp: 1688738360 Timestamp [UCT]: 2023-07-07 13:59:20 Age [y:d:h:m:s]: 01:196:04:41:06
Block: 798646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401540 RingCT/type: yes/0
Extra: 01c0d9e458a2d4e48ae0cdf274cda45e1468f661ef9fcc858e707c50f7040beab5021100000003faf35c9c000000000000000000

1 output(s) for total of 1.385971820000 dcy

stealth address amount amount idx
00: 1b26ef64ccb6de79132f1db09cd0d85d4cb60370bad3126acba9f0b25476c5f0 1.385971820000 1249597 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": 798656, "vin": [ { "gen": { "height": 798646 } } ], "vout": [ { "amount": 1385971820, "target": { "key": "1b26ef64ccb6de79132f1db09cd0d85d4cb60370bad3126acba9f0b25476c5f0" } } ], "extra": [ 1, 192, 217, 228, 88, 162, 212, 228, 138, 224, 205, 242, 116, 205, 164, 94, 20, 104, 246, 97, 239, 159, 204, 133, 142, 112, 124, 80, 247, 4, 11, 234, 181, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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