Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 989ce768933a0a4dd48de1ad99434e90fe23efabd5c2af551cb66b7d107ab324

Tx prefix hash: 941d6c90f833adff680fc748c5c373e03a02240502413947934bc48c52197d13
Tx public key: aa5f74febcbcb91420b194de6d1c41869a5ad6bc3d10560d1d2dc78b50f23a0c
Timestamp: 1728585035 Timestamp [UCT]: 2024-10-10 18:30:35 Age [y:d:h:m:s]: 00:174:09:05:21
Block: 1128727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124404 RingCT/type: yes/0
Extra: 01aa5f74febcbcb91420b194de6d1c41869a5ad6bc3d10560d1d2dc78b50f23a0c02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 573894288d16ba0dbad8ce8a19bbdcab5f32cb35d0704baec79a3bbd133d6cba 0.600000000000 1611548 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": 1128737, "vin": [ { "gen": { "height": 1128727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "573894288d16ba0dbad8ce8a19bbdcab5f32cb35d0704baec79a3bbd133d6cba" } } ], "extra": [ 1, 170, 95, 116, 254, 188, 188, 185, 20, 32, 177, 148, 222, 109, 28, 65, 134, 154, 90, 214, 188, 61, 16, 86, 13, 29, 45, 199, 139, 80, 242, 58, 12, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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