Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2ec6ffc2982c60fd57aa20f12d288c297691cd2fb8cfe1ad14e5231d621113a

Tx prefix hash: 5334132d968a892fed2eb840866587d20ce46e333d4cdb46d63f8d200bf36085
Tx public key: aa0cf8ee1eda14a70a0930bb8a52c677672d8fa358451dd42b4b0a889a47bfc5
Timestamp: 1581250464 Timestamp [UCT]: 2020-02-09 12:14:24 Age [y:d:h:m:s]: 05:077:02:38:13
Block: 61368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1207850 RingCT/type: yes/0
Extra: 01aa0cf8ee1eda14a70a0930bb8a52c677672d8fa358451dd42b4b0a889a47bfc50211000000217adf42d3000000000000000000

1 output(s) for total of 384.293604818000 dcy

stealth address amount amount idx
00: e0ae383be4e917fb511163baaf90f73b5768f25f55a175e9d6349ababd30d1ce 384.293604818000 113076 of 0

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": 61378, "vin": [ { "gen": { "height": 61368 } } ], "vout": [ { "amount": 384293604818, "target": { "key": "e0ae383be4e917fb511163baaf90f73b5768f25f55a175e9d6349ababd30d1ce" } } ], "extra": [ 1, 170, 12, 248, 238, 30, 218, 20, 167, 10, 9, 48, 187, 138, 82, 198, 119, 103, 45, 143, 163, 88, 69, 29, 212, 43, 75, 10, 136, 154, 71, 191, 197, 2, 17, 0, 0, 0, 33, 122, 223, 66, 211, 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