Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9693166b36ca588ca0f408c1454aaf3a95aa2492273ea4826e25116942cc6a0f

Tx prefix hash: ad41d14a52ab44c79419f7b7f5f8bad67f63e1c8dc65685035bb14949fca2ed6
Tx public key: 29ac1fb817627d9105c4f04a96d2a4de8555811ab852e7789d8404896c4c66a3
Timestamp: 1721641908 Timestamp [UCT]: 2024-07-22 09:51:48 Age [y:d:h:m:s]: 00:250:22:34:24
Block: 1071164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179256 RingCT/type: yes/0
Extra: 0129ac1fb817627d9105c4f04a96d2a4de8555811ab852e7789d8404896c4c66a302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eab5a2eca3d4d8b394aeea2959735e8b3b7895fe7e4d7919bae1ec34ccc33404 0.600000000000 1543285 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": 1071174, "vin": [ { "gen": { "height": 1071164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eab5a2eca3d4d8b394aeea2959735e8b3b7895fe7e4d7919bae1ec34ccc33404" } } ], "extra": [ 1, 41, 172, 31, 184, 23, 98, 125, 145, 5, 196, 240, 74, 150, 210, 164, 222, 133, 85, 129, 26, 184, 82, 231, 120, 157, 132, 4, 137, 108, 76, 102, 163, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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