Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 855fc0838662ca0492516a137ac653a77c14478b6a6bc11982471ed2d27c8e86

Tx prefix hash: 77abea041514a3edf63be0e3b6ffd91e4d1f278df71c4ec9ec373ae5fa4b2561
Tx public key: 72a9ca600e7bf9f20bc80e6eff7809b81428caffd657a2bb3b9aeab267dd6bc9
Timestamp: 1735624256 Timestamp [UCT]: 2024-12-31 05:50:56 Age [y:d:h:m:s]: 00:098:08:11:42
Block: 1186956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70071 RingCT/type: yes/0
Extra: 0172a9ca600e7bf9f20bc80e6eff7809b81428caffd657a2bb3b9aeab267dd6bc90211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 052d3226be069210f2f2b4f3a6c63d42b5ae9824553d4685d6ca2f5be94fb896 0.600000000000 1673441 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": 1186966, "vin": [ { "gen": { "height": 1186956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "052d3226be069210f2f2b4f3a6c63d42b5ae9824553d4685d6ca2f5be94fb896" } } ], "extra": [ 1, 114, 169, 202, 96, 14, 123, 249, 242, 11, 200, 14, 110, 255, 120, 9, 184, 20, 40, 202, 255, 214, 87, 162, 187, 59, 154, 234, 178, 103, 221, 107, 201, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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