Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23662241e870a4ce04a8ee3eb6f83111664a314486de4a9c2af04ba4097c4347

Tx prefix hash: dbaf820d5f116af2f7e43156d256f263b9df40558e377b0f07d6c501ef271b58
Tx public key: 34dd3f4b678a74aba168a8b531b83cf7f7ddc8eff87f651e1fbb65d1ce018386
Timestamp: 1717842724 Timestamp [UCT]: 2024-06-08 10:32:04 Age [y:d:h:m:s]: 00:282:02:14:28
Block: 1039679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201601 RingCT/type: yes/0
Extra: 0134dd3f4b678a74aba168a8b531b83cf7f7ddc8eff87f651e1fbb65d1ce01838602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21c70b17d13a3a4565cbfe5f9a56007f33d7e038b0947c15e59a3d5f36d236f6 0.600000000000 1508328 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": 1039689, "vin": [ { "gen": { "height": 1039679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21c70b17d13a3a4565cbfe5f9a56007f33d7e038b0947c15e59a3d5f36d236f6" } } ], "extra": [ 1, 52, 221, 63, 75, 103, 138, 116, 171, 161, 104, 168, 181, 49, 184, 60, 247, 247, 221, 200, 239, 248, 127, 101, 30, 31, 187, 101, 209, 206, 1, 131, 134, 2, 17, 0, 0, 0, 3, 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