Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f4e44104732aa94efddfd0f5a8beb775cf80705551c6ea8591856f713adacfc

Tx prefix hash: 07b6fbacc220636d58dccf6748ce8ab313a839bd184a86d3b13c10b339565d84
Tx public key: ec4cd1a5e94744831de4f56f26a045f168cfdb9ac9d33698df63070eaf8e6812
Timestamp: 1706442122 Timestamp [UCT]: 2024-01-28 11:42:02 Age [y:d:h:m:s]: 01:080:22:37:58
Block: 945126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318949 RingCT/type: yes/0
Extra: 01ec4cd1a5e94744831de4f56f26a045f168cfdb9ac9d33698df63070eaf8e681202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0be0021bede6f7fb4c8c9af6c6a76edb9499409381e4bfd768eeb3a31a1c9ae9 0.600000000000 1403436 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": 945136, "vin": [ { "gen": { "height": 945126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0be0021bede6f7fb4c8c9af6c6a76edb9499409381e4bfd768eeb3a31a1c9ae9" } } ], "extra": [ 1, 236, 76, 209, 165, 233, 71, 68, 131, 29, 228, 245, 111, 38, 160, 69, 241, 104, 207, 219, 154, 201, 211, 54, 152, 223, 99, 7, 14, 175, 142, 104, 18, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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