Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9c768ed7711a7e9ddec8b9842302e695f92ae1f52eadde8b951c43d45cdd966

Tx prefix hash: c0b97f62e08c7fba477333d7402f1da65d6781f3ddbbcf242165d2d002eead71
Tx public key: 91ad976b9cee9554c50c4fdc864ee7e196c7094e744f7aa757f276e957d61d6a
Timestamp: 1705245603 Timestamp [UCT]: 2024-01-14 15:20:03 Age [y:d:h:m:s]: 01:304:11:55:57
Block: 935230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476441 RingCT/type: yes/0
Extra: 0191ad976b9cee9554c50c4fdc864ee7e196c7094e744f7aa757f276e957d61d6a02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ad39f8be86602261bec86d7b9541dc45d31988e1359ea257456860815539283 0.600000000000 1393246 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": 935240, "vin": [ { "gen": { "height": 935230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ad39f8be86602261bec86d7b9541dc45d31988e1359ea257456860815539283" } } ], "extra": [ 1, 145, 173, 151, 107, 156, 238, 149, 84, 197, 12, 79, 220, 134, 78, 231, 225, 150, 199, 9, 78, 116, 79, 122, 167, 87, 242, 118, 233, 87, 214, 29, 106, 2, 17, 0, 0, 0, 7, 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