Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f13db26094da2e4f54c514376121a503c9bb08fb6743bbe99c7a4f1866adecea

Tx prefix hash: 2a815ea9e8a3afa0991c6b24eacf67684a9215a5449b028104a1f35957e8a79a
Tx public key: 531f6ed0b522fec79c9757c248ee2f206b139ec981dd3ff952c7d7c6efb5ac08
Timestamp: 1735150226 Timestamp [UCT]: 2024-12-25 18:10:26 Age [y:d:h:m:s]: 00:095:23:28:20
Block: 1183040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68373 RingCT/type: yes/0
Extra: 01531f6ed0b522fec79c9757c248ee2f206b139ec981dd3ff952c7d7c6efb5ac08021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12408c7f624c9d23061adced49735e8a1d2d66efa6c30ad0bf3033e57affa43c 0.600000000000 1669479 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": 1183050, "vin": [ { "gen": { "height": 1183040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12408c7f624c9d23061adced49735e8a1d2d66efa6c30ad0bf3033e57affa43c" } } ], "extra": [ 1, 83, 31, 110, 208, 181, 34, 254, 199, 156, 151, 87, 194, 72, 238, 47, 32, 107, 19, 158, 201, 129, 221, 63, 249, 82, 199, 215, 198, 239, 181, 172, 8, 2, 17, 0, 0, 0, 5, 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