Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb0c168c270d8dbb6a81a855842eb8f02bbf6ec144fef9b0c558397ef45f47e7

Tx prefix hash: 0b18b6aadaf488d254348405b75b0a73428e619e35318cbdfc13ca187f070ab4
Tx public key: 2575508378b57216c3b88fb3d9c34cd41bb7bd1e66999f287c4a21f215e5e181
Timestamp: 1711340961 Timestamp [UCT]: 2024-03-25 04:29:21 Age [y:d:h:m:s]: 01:035:14:38:29
Block: 985792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286417 RingCT/type: yes/0
Extra: 012575508378b57216c3b88fb3d9c34cd41bb7bd1e66999f287c4a21f215e5e1810211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e58b1574e11fc23bba1df932d6a05cfa651b5a1cb41541def3c0ac45c7791185 0.600000000000 1446011 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": 985802, "vin": [ { "gen": { "height": 985792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e58b1574e11fc23bba1df932d6a05cfa651b5a1cb41541def3c0ac45c7791185" } } ], "extra": [ 1, 37, 117, 80, 131, 120, 181, 114, 22, 195, 184, 143, 179, 217, 195, 76, 212, 27, 183, 189, 30, 102, 153, 159, 40, 124, 74, 33, 242, 21, 229, 225, 129, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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