Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2e3effb2deb0e2327d055165986b092713c3e93f75977f2c2488036a3082a5a

Tx prefix hash: 7a9a5103b8b4c727bc3670988bb8b17b8cdabcb400f24d9d6fbccd32a58ad373
Tx public key: f56abee284dd1708fbe6d939dc4c63df6e2b439216ba5f384b61b9d386b8dc00
Timestamp: 1727938005 Timestamp [UCT]: 2024-10-03 06:46:45 Age [y:d:h:m:s]: 00:251:20:39:25
Block: 1123370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179810 RingCT/type: yes/0
Extra: 01f56abee284dd1708fbe6d939dc4c63df6e2b439216ba5f384b61b9d386b8dc0002110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 722f7d1fc614420f4910ef3d1e3f5b347845a7f2ac5968e4d39ccba0baf65af5 0.600000000000 1605903 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": 1123380, "vin": [ { "gen": { "height": 1123370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "722f7d1fc614420f4910ef3d1e3f5b347845a7f2ac5968e4d39ccba0baf65af5" } } ], "extra": [ 1, 245, 106, 190, 226, 132, 221, 23, 8, 251, 230, 217, 57, 220, 76, 99, 223, 110, 43, 67, 146, 22, 186, 95, 56, 75, 97, 185, 211, 134, 184, 220, 0, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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