Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0521295284ac4f15d59ca704ce129e989d68a422e860bf8eafe8a33e2d750dc

Tx prefix hash: b1ab45651d8a4fd72e840596ea739b9f6592cd287c48333a10c4017a0d6090d9
Tx public key: a5fe74b1a8d2eddbe689ad8825c23bce96e9e46d604e38dcf804fcb996ed49aa
Timestamp: 1732648744 Timestamp [UCT]: 2024-11-26 19:19:04 Age [y:d:h:m:s]: 00:134:13:15:12
Block: 1162319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95981 RingCT/type: yes/0
Extra: 01a5fe74b1a8d2eddbe689ad8825c23bce96e9e46d604e38dcf804fcb996ed49aa0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11a8fc95b60ab78a07c7541c629357715a6d876e22a9d21bd4e6426b7e8479f2 0.600000000000 1647974 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": 1162329, "vin": [ { "gen": { "height": 1162319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11a8fc95b60ab78a07c7541c629357715a6d876e22a9d21bd4e6426b7e8479f2" } } ], "extra": [ 1, 165, 254, 116, 177, 168, 210, 237, 219, 230, 137, 173, 136, 37, 194, 59, 206, 150, 233, 228, 109, 96, 78, 56, 220, 248, 4, 252, 185, 150, 237, 73, 170, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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