Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 755f532486c46823ec593635d0a85e08d6e475358d6cf0af6a1a8765dd299752

Tx prefix hash: 609434e4f990b77ee945fbc6213d334c5c86b1ce47f676f37bc1516ac351eba8
Tx public key: 6b473ada9c146b039296cb4b9beb725e607aa271fb475c5f41e05aa96a4b3071
Timestamp: 1750281282 Timestamp [UCT]: 2025-06-18 21:14:42 Age [y:d:h:m:s]: 00:154:17:07:41
Block: 1307893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108391 RingCT/type: yes/0
Extra: 016b473ada9c146b039296cb4b9beb725e607aa271fb475c5f41e05aa96a4b3071021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6f96ef7cfaeda3e0af1992f4ea2b84dcaf3b9aa0aa9a2a2664a03df0f3fc114 0.600000000000 1795504 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": 1307903, "vin": [ { "gen": { "height": 1307893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6f96ef7cfaeda3e0af1992f4ea2b84dcaf3b9aa0aa9a2a2664a03df0f3fc114" } } ], "extra": [ 1, 107, 71, 58, 218, 156, 20, 107, 3, 146, 150, 203, 75, 155, 235, 114, 94, 96, 122, 162, 113, 251, 71, 92, 95, 65, 224, 90, 169, 106, 75, 48, 113, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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