Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22a9e4258f756d8293276cfc2f14ecb775244008c19eb51921b071c58f66689d

Tx prefix hash: 66881dd8b6d53c99079218b2486a73f54943eb0b5bbe6773af4727c5927bc6b4
Tx public key: a67e3c55c82ec60e429702e30957f7bb0bf640f2f22d7ee2520e1dc591c50afd
Timestamp: 1732055195 Timestamp [UCT]: 2024-11-19 22:26:35 Age [y:d:h:m:s]: 00:138:21:42:48
Block: 1157413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99073 RingCT/type: yes/0
Extra: 01a67e3c55c82ec60e429702e30957f7bb0bf640f2f22d7ee2520e1dc591c50afd0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0e5f738a5c877de9fda2fab46d440b125baab04d9adecd3dda4b0134207821e 0.600000000000 1643036 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": 1157423, "vin": [ { "gen": { "height": 1157413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0e5f738a5c877de9fda2fab46d440b125baab04d9adecd3dda4b0134207821e" } } ], "extra": [ 1, 166, 126, 60, 85, 200, 46, 198, 14, 66, 151, 2, 227, 9, 87, 247, 187, 11, 246, 64, 242, 242, 45, 126, 226, 82, 14, 29, 197, 145, 197, 10, 253, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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