Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98379284dca77072a63e7f12b4e3670f929a765ce7031f3d85b7acc21e0d58cb

Tx prefix hash: 26aa4b638b03e52a5f1dc53be335522f3321289dc91d3b47229d7a1bed85717f
Tx public key: 6db23f15da6a5e568a895e9230b81a9d1f704fe7361c6370090886860c3a5d59
Timestamp: 1706685050 Timestamp [UCT]: 2024-01-31 07:10:50 Age [y:d:h:m:s]: 01:066:08:09:10
Block: 947148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308477 RingCT/type: yes/0
Extra: 016db23f15da6a5e568a895e9230b81a9d1f704fe7361c6370090886860c3a5d5902110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3aa93063d196947c90b59d6b9fbb62788046ddae8af81708160d630a2837a73b 0.600000000000 1405496 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": 947158, "vin": [ { "gen": { "height": 947148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3aa93063d196947c90b59d6b9fbb62788046ddae8af81708160d630a2837a73b" } } ], "extra": [ 1, 109, 178, 63, 21, 218, 106, 94, 86, 138, 137, 94, 146, 48, 184, 26, 157, 31, 112, 79, 231, 54, 28, 99, 112, 9, 8, 134, 134, 12, 58, 93, 89, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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