Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 564fd84a98264676e06e8632e0e81e90130d71a02fb808d4071519c65bab6953

Tx prefix hash: ecb52891181d5f916aaed877a2501cbea9dc112c45f658180c2b64d750d3acd3
Tx public key: 0d741a4e1d5d127c5b279dd9ccdd0d66679b51da0c23f94b06036e0811bd04ad
Timestamp: 1713532379 Timestamp [UCT]: 2024-04-19 13:12:59 Age [y:d:h:m:s]: 00:253:19:00:35
Block: 1003930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181665 RingCT/type: yes/0
Extra: 010d741a4e1d5d127c5b279dd9ccdd0d66679b51da0c23f94b06036e0811bd04ad021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bc4f21ceaa0306a99ddc1c9c292dd90759ff3660537cebe2d41bb19e861a04d 0.600000000000 1464484 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": 1003940, "vin": [ { "gen": { "height": 1003930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bc4f21ceaa0306a99ddc1c9c292dd90759ff3660537cebe2d41bb19e861a04d" } } ], "extra": [ 1, 13, 116, 26, 78, 29, 93, 18, 124, 91, 39, 157, 217, 204, 221, 13, 102, 103, 155, 81, 218, 12, 35, 249, 75, 6, 3, 110, 8, 17, 189, 4, 173, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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