Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8811a47ed82152141e31adf0a988202e33f622b93ae7d1899de7d620cd2bc477

Tx prefix hash: d19a579d60528a2e2901ade32f8bb0746e74144f88d0fd47efb3f5d7e321963f
Tx public key: 31103931ac47f4230d2f4e86cda0065165e9cdcdca0a404a4bc3bbb27e8c189a
Timestamp: 1723219374 Timestamp [UCT]: 2024-08-09 16:02:54 Age [y:d:h:m:s]: 00:244:18:56:57
Block: 1084246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174850 RingCT/type: yes/0
Extra: 0131103931ac47f4230d2f4e86cda0065165e9cdcdca0a404a4bc3bbb27e8c189a021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88349b61fdc8d184e057d1f0bf19bb8d5b563cc2f3ebee3e92aa019db103d41d 0.600000000000 1558451 of 15

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": 1084256, "vin": [ { "gen": { "height": 1084246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88349b61fdc8d184e057d1f0bf19bb8d5b563cc2f3ebee3e92aa019db103d41d" } } ], "extra": [ 1, 49, 16, 57, 49, 172, 71, 244, 35, 13, 47, 78, 134, 205, 160, 6, 81, 101, 233, 205, 205, 202, 10, 64, 74, 75, 195, 187, 178, 126, 140, 24, 154, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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