Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac0fcbbe163c0c73fd89d932292513aedb2eebbb5257e874d7d134a79308fdc9

Tx prefix hash: c2f4b4fe6ab7e43242ce9e594038bcb1dbc339701b9f24c362a094ce05331803
Tx public key: 0a5fc469a0f1e79285c807686aa5a30f109243d7378dc1d0d641e89f1e84a6b9
Timestamp: 1723412300 Timestamp [UCT]: 2024-08-11 21:38:20 Age [y:d:h:m:s]: 00:235:04:19:23
Block: 1085844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167956 RingCT/type: yes/0
Extra: 010a5fc469a0f1e79285c807686aa5a30f109243d7378dc1d0d641e89f1e84a6b902110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2410a096bec4184c54d64d6dfda08f9f98ac1e2d1d16376ee3ab4566c408c8b 0.600000000000 1560435 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": 1085854, "vin": [ { "gen": { "height": 1085844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2410a096bec4184c54d64d6dfda08f9f98ac1e2d1d16376ee3ab4566c408c8b" } } ], "extra": [ 1, 10, 95, 196, 105, 160, 241, 231, 146, 133, 200, 7, 104, 106, 165, 163, 15, 16, 146, 67, 215, 55, 141, 193, 208, 214, 65, 232, 159, 30, 132, 166, 185, 2, 17, 0, 0, 0, 5, 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