Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3de45cec3199cfcf56296a4a7b883e3b91936b069695142a401e07a7243f606

Tx prefix hash: 7cfe1b8468ec869d1a518f3ce1f19f7468ac2f50e793aa3320177dd57b4cb364
Tx public key: 939be07e980c5e631e0d50111c8eac713875e43a0600594ad43a9abf0ca800ba
Timestamp: 1734427799 Timestamp [UCT]: 2024-12-17 09:29:59 Age [y:d:h:m:s]: 00:092:13:57:11
Block: 1177079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65954 RingCT/type: yes/0
Extra: 01939be07e980c5e631e0d50111c8eac713875e43a0600594ad43a9abf0ca800ba0211000000101f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd08ee9bb6851ae8918b985c88dc7b93d0e98aebc0d1ae635ed6af0219d2a846 0.600000000000 1663442 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": 1177089, "vin": [ { "gen": { "height": 1177079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd08ee9bb6851ae8918b985c88dc7b93d0e98aebc0d1ae635ed6af0219d2a846" } } ], "extra": [ 1, 147, 155, 224, 126, 152, 12, 94, 99, 30, 13, 80, 17, 28, 142, 172, 113, 56, 117, 228, 58, 6, 0, 89, 74, 212, 58, 154, 191, 12, 168, 0, 186, 2, 17, 0, 0, 0, 16, 31, 10, 83, 235, 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