Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e398599c88343abb051f15412bd81e1a2b9a0f13f84fa46feaf8fdb89fd7c87

Tx prefix hash: c0bc3f36deb6b89720e647e580ce2cbb1c934b8d5530f7eed8736e49cfcd9e20
Tx public key: f6b104d5fc17cd96c814f0502ea896d8b558d4c281f8d0a75ae8af8100685d5e
Timestamp: 1721346122 Timestamp [UCT]: 2024-07-18 23:42:02 Age [y:d:h:m:s]: 00:261:22:30:49
Block: 1068731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187098 RingCT/type: yes/0
Extra: 01f6b104d5fc17cd96c814f0502ea896d8b558d4c281f8d0a75ae8af8100685d5e021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8afdfc4151c6d892f0c8022c404e23695e7b76a03f5baf26f4ffd3aed4471b90 0.600000000000 1539876 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": 1068741, "vin": [ { "gen": { "height": 1068731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8afdfc4151c6d892f0c8022c404e23695e7b76a03f5baf26f4ffd3aed4471b90" } } ], "extra": [ 1, 246, 177, 4, 213, 252, 23, 205, 150, 200, 20, 240, 80, 46, 168, 150, 216, 181, 88, 212, 194, 129, 248, 208, 167, 90, 232, 175, 129, 0, 104, 93, 94, 2, 17, 0, 0, 0, 3, 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