Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea85a187ddee1576585e90d0b79e98b7c320c344203b8f74c5e1b79718b58e1d

Tx prefix hash: 548e6b4116248843f0b4053d06ba781d9e0988a21dfa142e9c0111a4500d00a6
Tx public key: 699a69d2a23ca88c6a4d9b3bb5ce5cde5b4d1a47c3a4a6cb54f0e6e17345dff8
Timestamp: 1685815019 Timestamp [UCT]: 2023-06-03 17:56:59 Age [y:d:h:m:s]: 01:165:07:53:21
Block: 774386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379534 RingCT/type: yes/0
Extra: 01699a69d2a23ca88c6a4d9b3bb5ce5cde5b4d1a47c3a4a6cb54f0e6e17345dff802110000000133af99f4000000000000000000

1 output(s) for total of 1.667776640000 dcy

stealth address amount amount idx
00: 4901369de6782b8cf44dd08eeb2f6d47f47cf17cc842f780e6221107bc484779 1.667776640000 1223861 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": 774396, "vin": [ { "gen": { "height": 774386 } } ], "vout": [ { "amount": 1667776640, "target": { "key": "4901369de6782b8cf44dd08eeb2f6d47f47cf17cc842f780e6221107bc484779" } } ], "extra": [ 1, 105, 154, 105, 210, 162, 60, 168, 140, 106, 77, 155, 59, 181, 206, 92, 222, 91, 77, 26, 71, 195, 164, 166, 203, 84, 240, 230, 225, 115, 69, 223, 248, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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