Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1482a0343909b5de561c70cd7b6bc57499b5cf03bfa60224a7c234f8eb16b837

Tx prefix hash: 9422915a5fd0c6ef70d94a59c5666809ce6b63f780f421cbd9bea8682d5b973b
Tx public key: 10a3989887e1d54700d9f5ae1a98377e855a0bd4d4c4f3c84a72d61d6756fa10
Timestamp: 1723817752 Timestamp [UCT]: 2024-08-16 14:15:52 Age [y:d:h:m:s]: 00:237:08:34:01
Block: 1089214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169506 RingCT/type: yes/0
Extra: 0110a3989887e1d54700d9f5ae1a98377e855a0bd4d4c4f3c84a72d61d6756fa10021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a2cad1809014e352d129ab40f63b0ba7ca16d3599decb9a5ffe71e7191d6243 0.600000000000 1563833 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": 1089224, "vin": [ { "gen": { "height": 1089214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a2cad1809014e352d129ab40f63b0ba7ca16d3599decb9a5ffe71e7191d6243" } } ], "extra": [ 1, 16, 163, 152, 152, 135, 225, 213, 71, 0, 217, 245, 174, 26, 152, 55, 126, 133, 90, 11, 212, 212, 196, 243, 200, 74, 114, 214, 29, 103, 86, 250, 16, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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