Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dc5d88cdb48b244a23bd0f47047b40e6733773a57e2a86abf33cda9d8ca75bc

Tx prefix hash: 95d4c6c26008f3ed000cd0456249daa971ad7af158ce1ecf4a5b12d23e694796
Tx public key: 683a549a4c1816674186c6231b6db33576e031ed3d2fef4f16314f9c560a9091
Timestamp: 1760921841 Timestamp [UCT]: 2025-10-20 00:57:21 Age [y:d:h:m:s]: 00:074:09:01:04
Block: 1393720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53236 RingCT/type: yes/0
Extra: 01683a549a4c1816674186c6231b6db33576e031ed3d2fef4f16314f9c560a90910211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06b9e49827ce3dbce3d293c8a0195b7ea79958306cc32c95316018bbc62f90be 0.600000000000 1881985 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": 1393730, "vin": [ { "gen": { "height": 1393720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06b9e49827ce3dbce3d293c8a0195b7ea79958306cc32c95316018bbc62f90be" } } ], "extra": [ 1, 104, 58, 84, 154, 76, 24, 22, 103, 65, 134, 198, 35, 27, 109, 179, 53, 118, 224, 49, 237, 61, 47, 239, 79, 22, 49, 79, 156, 86, 10, 144, 145, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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