Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ac4356f3d1f55905e5d6454340c2c7bc13fd72b87389226df955fd3653a0fa5

Tx prefix hash: 32b9b8c67852dfbba44e97c256317b72e5c1fbf419417b231322a2c10aab886f
Tx public key: 43f80a52271e22d8042b9f5254981350c17fc85251f77bb81e5d917baf98c4e7
Timestamp: 1705142872 Timestamp [UCT]: 2024-01-13 10:47:52 Age [y:d:h:m:s]: 01:154:00:54:25
Block: 934364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371143 RingCT/type: yes/0
Extra: 0143f80a52271e22d8042b9f5254981350c17fc85251f77bb81e5d917baf98c4e70211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b6c300f3bdee307141ff46c2bf5359ab84d47f4f06a9c34b97c16c8fde2880b 0.600000000000 1392370 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": 934374, "vin": [ { "gen": { "height": 934364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b6c300f3bdee307141ff46c2bf5359ab84d47f4f06a9c34b97c16c8fde2880b" } } ], "extra": [ 1, 67, 248, 10, 82, 39, 30, 34, 216, 4, 43, 159, 82, 84, 152, 19, 80, 193, 127, 200, 82, 81, 247, 123, 184, 30, 93, 145, 123, 175, 152, 196, 231, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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