Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e241aacdf002890ae26374c0180800dc56052f869d3151bd33eac06ea23fa7c

Tx prefix hash: 943958c4bed5fc82bf3dc7858103836a6883cb46ee47c283a1782a66d830f81b
Tx public key: c96eafe717f2712770c7f27d8bcceae4e6b81add60280305121d85d4db46b4e5
Timestamp: 1744552177 Timestamp [UCT]: 2025-04-13 13:49:37 Age [y:d:h:m:s]: 00:222:03:05:38
Block: 1260601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156478 RingCT/type: yes/0
Extra: 01c96eafe717f2712770c7f27d8bcceae4e6b81add60280305121d85d4db46b4e50211000000066c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f4f3172a8903f19c0d4f8cf19c7e3afc0808d9d3138670e41e4d3550bff6b6b 0.600000000000 1747760 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": 1260611, "vin": [ { "gen": { "height": 1260601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f4f3172a8903f19c0d4f8cf19c7e3afc0808d9d3138670e41e4d3550bff6b6b" } } ], "extra": [ 1, 201, 110, 175, 231, 23, 242, 113, 39, 112, 199, 242, 125, 139, 204, 234, 228, 230, 184, 26, 221, 96, 40, 3, 5, 18, 29, 133, 212, 219, 70, 180, 229, 2, 17, 0, 0, 0, 6, 108, 152, 170, 61, 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