Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df50b9f3aed8394df626983c1909760321a814e833c4edaa6fc3cd5b49c3806a

Tx prefix hash: 201c5a15809815f5a35fbc73fa86c3d1d60d58bc3d96a66b3d7e6230b1570a0d
Tx public key: 9ed85db7fb1c74c3de29c3226327b27ca0d5a9d98174b6ef82e234ae5202321f
Timestamp: 1720368303 Timestamp [UCT]: 2024-07-07 16:05:03 Age [y:d:h:m:s]: 01:129:06:02:44
Block: 1060604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350909 RingCT/type: yes/0
Extra: 019ed85db7fb1c74c3de29c3226327b27ca0d5a9d98174b6ef82e234ae5202321f021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c3ff494e9d5e5600e249a6c33c8a3ccca23f9d0299d7f85c2d5af09d9582569 0.600000000000 1531089 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": 1060614, "vin": [ { "gen": { "height": 1060604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c3ff494e9d5e5600e249a6c33c8a3ccca23f9d0299d7f85c2d5af09d9582569" } } ], "extra": [ 1, 158, 216, 93, 183, 251, 28, 116, 195, 222, 41, 195, 34, 99, 39, 178, 124, 160, 213, 169, 217, 129, 116, 182, 239, 130, 226, 52, 174, 82, 2, 50, 31, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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