Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80e216b11f4b80ce503b0faf72784ad0c19d954d1d298fbc22c69d771e4428ce

Tx prefix hash: 79063834bdfa8b977cca7dc67a728af5e7d28229dc6bca94acea2af3a8a75d81
Tx public key: 69643d774bda3f3fe207a6fba3e9ac62b3fe9b9fb45b7ae02df595fb21aab023
Timestamp: 1702610581 Timestamp [UCT]: 2023-12-15 03:23:01 Age [y:d:h:m:s]: 01:330:21:03:34
Block: 913384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495336 RingCT/type: yes/0
Extra: 0169643d774bda3f3fe207a6fba3e9ac62b3fe9b9fb45b7ae02df595fb21aab023021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71143a9c26cfd8c5c3aec1974dec34626823005c9bae5c2b9d99e2a3135ca2c5 0.600000000000 1370652 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": 913394, "vin": [ { "gen": { "height": 913384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71143a9c26cfd8c5c3aec1974dec34626823005c9bae5c2b9d99e2a3135ca2c5" } } ], "extra": [ 1, 105, 100, 61, 119, 75, 218, 63, 63, 226, 7, 166, 251, 163, 233, 172, 98, 179, 254, 155, 159, 180, 91, 122, 224, 45, 245, 149, 251, 33, 170, 176, 35, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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