Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a33102e09e68ec6d5b275201f4b34e6fbc6f2d517ed9aa89e4bd9e77507aecdc

Tx prefix hash: 073c10538c17088ce1855fbe8f0f56912e3abc4d25f93d20768f896f38e581c9
Tx public key: fed3fb1eb1c4c7a47defa6c58254d63591ca66573db37ff77cb4760d1ce469a6
Timestamp: 1705150073 Timestamp [UCT]: 2024-01-13 12:47:53 Age [y:d:h:m:s]: 02:014:04:18:30
Block: 934429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 529746 RingCT/type: yes/0
Extra: 01fed3fb1eb1c4c7a47defa6c58254d63591ca66573db37ff77cb4760d1ce469a602110000000c0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40ef5512fc34a078855e0f03d0f426279383babfbb2582aa4ce683e33efc0b47 0.600000000000 1392437 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": 934439, "vin": [ { "gen": { "height": 934429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40ef5512fc34a078855e0f03d0f426279383babfbb2582aa4ce683e33efc0b47" } } ], "extra": [ 1, 254, 211, 251, 30, 177, 196, 199, 164, 125, 239, 166, 197, 130, 84, 214, 53, 145, 202, 102, 87, 61, 179, 127, 247, 124, 180, 118, 13, 28, 228, 105, 166, 2, 17, 0, 0, 0, 12, 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