Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b88d13d969f8d748f5d564f003a4b2897dbdff48df645be35ef543b7c54b13a

Tx prefix hash: d492f27225c13dae257422f85589f23af8a9d251f9e5b0846230a99de9b8ee61
Tx public key: 0b2930affc128ed86472ffca60c1f7b145be7434233df51f14f668fb6ec7d3e2
Timestamp: 1694480742 Timestamp [UCT]: 2023-09-12 01:05:42 Age [y:d:h:m:s]: 01:127:14:45:30
Block: 846169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352532 RingCT/type: yes/0
Extra: 010b2930affc128ed86472ffca60c1f7b145be7434233df51f14f668fb6ec7d3e20211000000024b8f5122000000000000000000

1 output(s) for total of 0.964474842000 dcy

stealth address amount amount idx
00: 0bff91093cca624ce31a4d82a3faf9d0383b84c0d1aba0e74acd2015e600fd8e 0.964474842000 1299615 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": 846179, "vin": [ { "gen": { "height": 846169 } } ], "vout": [ { "amount": 964474842, "target": { "key": "0bff91093cca624ce31a4d82a3faf9d0383b84c0d1aba0e74acd2015e600fd8e" } } ], "extra": [ 1, 11, 41, 48, 175, 252, 18, 142, 216, 100, 114, 255, 202, 96, 193, 247, 177, 69, 190, 116, 52, 35, 61, 245, 31, 20, 246, 104, 251, 110, 199, 211, 226, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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