Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d202f9b9775df1f888b09df3bd5e6bff69e4297a0f12053ffd0a160c6efe13d8

Tx prefix hash: a5477de1ea981a95dff79e909b1f2da3f6cf87bd7f6bfc62a825cb56320d37f8
Tx public key: ba369341a498a54f65e136fd31c6566b427824bd3422f2de2240272ceea60fe9
Timestamp: 1672036253 Timestamp [UCT]: 2022-12-26 06:30:53 Age [y:d:h:m:s]: 02:141:02:27:42
Block: 660794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 622555 RingCT/type: yes/0
Extra: 01ba369341a498a54f65e136fd31c6566b427824bd3422f2de2240272ceea60fe902110000000175e3f0e9000000000000000000

1 output(s) for total of 3.967483599000 dcy

stealth address amount amount idx
00: 1aab6a88f437270484a4b45fafc0d0c88634cd271803bd7063fbc406a09c4ee0 3.967483599000 1101533 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": 660804, "vin": [ { "gen": { "height": 660794 } } ], "vout": [ { "amount": 3967483599, "target": { "key": "1aab6a88f437270484a4b45fafc0d0c88634cd271803bd7063fbc406a09c4ee0" } } ], "extra": [ 1, 186, 54, 147, 65, 164, 152, 165, 79, 101, 225, 54, 253, 49, 198, 86, 107, 66, 120, 36, 189, 52, 34, 242, 222, 34, 64, 39, 44, 238, 166, 15, 233, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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