Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae15fe3564b64df661936d7fdbc01c504ae5cf9e65a17adcf83d84295d150c42

Tx prefix hash: cf6531fdcb5138b0cfdaf5b6bc8a0556fad2cecf323fd2ef01a87317719637b5
Tx public key: 8fb3ffd2aa74156e954173a4af6437ecde3be4f883eb6b99331cf85675fd1055
Timestamp: 1698030286 Timestamp [UCT]: 2023-10-23 03:04:46 Age [y:d:h:m:s]: 01:234:05:48:31
Block: 875616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428427 RingCT/type: yes/0
Extra: 018fb3ffd2aa74156e954173a4af6437ecde3be4f883eb6b99331cf85675fd105502110000000133af99f4000000000000000000

1 output(s) for total of 0.770407897000 dcy

stealth address amount amount idx
00: fded4d0274a33bddc5e0b147809662bc0d0f3439582310f19a8938bf632a2402 0.770407897000 1330880 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": 875626, "vin": [ { "gen": { "height": 875616 } } ], "vout": [ { "amount": 770407897, "target": { "key": "fded4d0274a33bddc5e0b147809662bc0d0f3439582310f19a8938bf632a2402" } } ], "extra": [ 1, 143, 179, 255, 210, 170, 116, 21, 110, 149, 65, 115, 164, 175, 100, 55, 236, 222, 59, 228, 248, 131, 235, 107, 153, 51, 28, 248, 86, 117, 253, 16, 85, 2, 17, 0, 0, 0, 1, 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