Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3495ffdde3fda298e2ea7b3407adc25871269e0f746649f87eead35dbcf90f8

Tx prefix hash: f63634df0cb0f1cf991437713b211ee28c274ac7d138f2c1e032db0ddc224ab0
Tx public key: 892308d6b5677139d8eca8fa8d5fb3b47ee1c26e0909883153ae074a5661f4a0
Timestamp: 1733687887 Timestamp [UCT]: 2024-12-08 19:58:07 Age [y:d:h:m:s]: 00:122:16:38:31
Block: 1170951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87470 RingCT/type: yes/0
Extra: 01892308d6b5677139d8eca8fa8d5fb3b47ee1c26e0909883153ae074a5661f4a0021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff4b21b137895fa13b94e9bfa46005d4df98e0f6f8add947bb39503363415239 0.600000000000 1656686 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": 1170961, "vin": [ { "gen": { "height": 1170951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff4b21b137895fa13b94e9bfa46005d4df98e0f6f8add947bb39503363415239" } } ], "extra": [ 1, 137, 35, 8, 214, 181, 103, 113, 57, 216, 236, 168, 250, 141, 95, 179, 180, 126, 225, 194, 110, 9, 9, 136, 49, 83, 174, 7, 74, 86, 97, 244, 160, 2, 17, 0, 0, 0, 4, 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