Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22251e162ab0f7b2795498a256274d4649954041e4f5e4f7b417850c573827c6

Tx prefix hash: b365578974fefba712749d1b3be7e24760100fd5f3d8898bfedf7e00baa56706
Tx public key: 845111946a8c3bab4fcdf30c44c8c91aacb63997541e408ee085bfd62290b0f7
Timestamp: 1731758710 Timestamp [UCT]: 2024-11-16 12:05:10 Age [y:d:h:m:s]: 00:188:09:24:51
Block: 1154958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134499 RingCT/type: yes/0
Extra: 01845111946a8c3bab4fcdf30c44c8c91aacb63997541e408ee085bfd62290b0f7021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 926ba55a3fa50f156fef1d3e176a1a8f7e0e5c2bfbf5b6e46ded4b1a730c3ffc 0.600000000000 1640571 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": 1154968, "vin": [ { "gen": { "height": 1154958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "926ba55a3fa50f156fef1d3e176a1a8f7e0e5c2bfbf5b6e46ded4b1a730c3ffc" } } ], "extra": [ 1, 132, 81, 17, 148, 106, 140, 59, 171, 79, 205, 243, 12, 68, 200, 201, 26, 172, 182, 57, 151, 84, 30, 64, 142, 224, 133, 191, 214, 34, 144, 176, 247, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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