Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88c2312f5aaff5638604f41d4d6c8d83fbc1a3b64f9103e13daf525469e7a586

Tx prefix hash: 5ee64c03aa148802e995ce960d78d79409d91bd0c42dec338a81c96e73badad0
Tx public key: d55aaea1cdeab96757fd3626ce9a4736500f366f5a32835b422603368c7c0ee9
Timestamp: 1709672015 Timestamp [UCT]: 2024-03-05 20:53:35 Age [y:d:h:m:s]: 01:307:15:12:09
Block: 971943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478663 RingCT/type: yes/0
Extra: 01d55aaea1cdeab96757fd3626ce9a4736500f366f5a32835b422603368c7c0ee90211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4c5c556e2e21d2e0e40c8173eb32c512c453c30e5da6e9ae8e38b700b5d67ed 0.600000000000 1431848 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": 971953, "vin": [ { "gen": { "height": 971943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4c5c556e2e21d2e0e40c8173eb32c512c453c30e5da6e9ae8e38b700b5d67ed" } } ], "extra": [ 1, 213, 90, 174, 161, 205, 234, 185, 103, 87, 253, 54, 38, 206, 154, 71, 54, 80, 15, 54, 111, 90, 50, 131, 91, 66, 38, 3, 54, 140, 124, 14, 233, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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