Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 931ad5af76288c464ed7e23abf6cae630c45b4f600efcc4ba971073b2ea94ef0

Tx prefix hash: d95997417ae18cf17db8be25ae0663b776d06c8f48c138ec180c0de641f0c16a
Tx public key: e039ec9d1aad7fa3910b8b40f189341f798fe9bee65949e1669ca1f4961a5e26
Timestamp: 1727165903 Timestamp [UCT]: 2024-09-24 08:18:23 Age [y:d:h:m:s]: 00:109:11:34:57
Block: 1116971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78261 RingCT/type: yes/0
Extra: 01e039ec9d1aad7fa3910b8b40f189341f798fe9bee65949e1669ca1f4961a5e2602110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae5aa145905b85793258c4d6b7a343da38b114cf4435d0cb05e7e42eedc7379e 0.600000000000 1597638 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": 1116981, "vin": [ { "gen": { "height": 1116971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae5aa145905b85793258c4d6b7a343da38b114cf4435d0cb05e7e42eedc7379e" } } ], "extra": [ 1, 224, 57, 236, 157, 26, 173, 127, 163, 145, 11, 139, 64, 241, 137, 52, 31, 121, 143, 233, 190, 230, 89, 73, 225, 102, 156, 161, 244, 150, 26, 94, 38, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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