Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 948db7cabfe3eb0b89adaf892394a316fbf34db1cd102f8f6ffa0863fddb9f5a

Tx prefix hash: e2957319a318b390eea57e5d984648ae1974b5f6ed8d0fe108587dab0542018d
Tx public key: b1a204cc1fb755d0beca3dc7b7834ef3647e5d402990e54a98b05c69a6ec7d1b
Timestamp: 1713172618 Timestamp [UCT]: 2024-04-15 09:16:58 Age [y:d:h:m:s]: 01:198:21:37:26
Block: 1000944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400820 RingCT/type: yes/0
Extra: 01b1a204cc1fb755d0beca3dc7b7834ef3647e5d402990e54a98b05c69a6ec7d1b0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e424e799d7a475899098e41737ddadd7987ede0fc65a283fafb5d915a6489ab7 0.600000000000 1461444 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": 1000954, "vin": [ { "gen": { "height": 1000944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e424e799d7a475899098e41737ddadd7987ede0fc65a283fafb5d915a6489ab7" } } ], "extra": [ 1, 177, 162, 4, 204, 31, 183, 85, 208, 190, 202, 61, 199, 183, 131, 78, 243, 100, 126, 93, 64, 41, 144, 229, 74, 152, 176, 92, 105, 166, 236, 125, 27, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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