Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c2a0bea507c9f175a4da823b241db5c7517b1f8c2f128f92e44773b9a9f0f32

Tx prefix hash: b0c66110c59dad4585f3157384ff198fc883c03987c91573a97fc09a5395ed04
Tx public key: 689fbca9e05836196e58f286223a1a6a1b03d6866dec9bc6ef22e034dba4913a
Timestamp: 1728883279 Timestamp [UCT]: 2024-10-14 05:21:19 Age [y:d:h:m:s]: 01:052:05:43:17
Block: 1131207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295740 RingCT/type: yes/0
Extra: 01689fbca9e05836196e58f286223a1a6a1b03d6866dec9bc6ef22e034dba4913a0211000000043cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63f1ca8f42403f6b3ee11c33d5054ef10b3bc149bfc161f3d7c0ca58d3132e64 0.600000000000 1614088 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": 1131217, "vin": [ { "gen": { "height": 1131207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63f1ca8f42403f6b3ee11c33d5054ef10b3bc149bfc161f3d7c0ca58d3132e64" } } ], "extra": [ 1, 104, 159, 188, 169, 224, 88, 54, 25, 110, 88, 242, 134, 34, 58, 26, 106, 27, 3, 214, 134, 109, 236, 155, 198, 239, 34, 224, 52, 219, 164, 145, 58, 2, 17, 0, 0, 0, 4, 60, 208, 252, 6, 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