Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e63ec6ccf829345358756f39568f6125d96d89eb6f194d3a8d6b6e70fc2c3f72

Tx prefix hash: 5fae97d241080ff142b21134a801e834de70f311531aad0b87b04d09c8cc4e0a
Tx public key: 5d1678c1961b51391d0ec70fbf944ba596bd2c253d6720e0f5e6a7efbe8dc7d1
Timestamp: 1581240928 Timestamp [UCT]: 2020-02-09 09:35:28 Age [y:d:h:m:s]: 04:295:12:35:21
Block: 61171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1103386 RingCT/type: yes/0
Extra: 015d1678c1961b51391d0ec70fbf944ba596bd2c253d6720e0f5e6a7efbe8dc7d10211000000094943cd9f000000000000000000

1 output(s) for total of 384.871631021000 dcy

stealth address amount amount idx
00: 36eba128378c05c5a5d3fd2593356550faa6b2a23ad8016465b58595046064ee 384.871631021000 112730 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": 61181, "vin": [ { "gen": { "height": 61171 } } ], "vout": [ { "amount": 384871631021, "target": { "key": "36eba128378c05c5a5d3fd2593356550faa6b2a23ad8016465b58595046064ee" } } ], "extra": [ 1, 93, 22, 120, 193, 150, 27, 81, 57, 29, 14, 199, 15, 191, 148, 75, 165, 150, 189, 44, 37, 61, 103, 32, 224, 245, 230, 167, 239, 190, 141, 199, 209, 2, 17, 0, 0, 0, 9, 73, 67, 205, 159, 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