Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd6688f5a24e5bd5670f47b930000887296388b0d79a5119cdf892269b9f4c00

Tx prefix hash: c76a8d1eee5c08f44fbd61fcc5948edee969c8f374b35f18a78ecdc0c6f30293
Tx public key: 005d87180e1b167c5e6fb437f9d527d59e09189e08a98ea86bb211ced0d7b63d
Timestamp: 1723473714 Timestamp [UCT]: 2024-08-12 14:41:54 Age [y:d:h:m:s]: 00:149:14:38:07
Block: 1086351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107033 RingCT/type: yes/0
Extra: 01005d87180e1b167c5e6fb437f9d527d59e09189e08a98ea86bb211ced0d7b63d021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0e6bb04e7085a354c400275d4bfb220d2121f49928323454b67557530e120a5 0.600000000000 1560948 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": 1086361, "vin": [ { "gen": { "height": 1086351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0e6bb04e7085a354c400275d4bfb220d2121f49928323454b67557530e120a5" } } ], "extra": [ 1, 0, 93, 135, 24, 14, 27, 22, 124, 94, 111, 180, 55, 249, 213, 39, 213, 158, 9, 24, 158, 8, 169, 142, 168, 107, 178, 17, 206, 208, 215, 182, 61, 2, 17, 0, 0, 0, 6, 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