Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c82c71e7123134065117b01883389c3ee3cb478d445a54fdf224120e28a668f4

Tx prefix hash: a570f56533fe409d8799d37e3971d2732e03a57c897a9003b13df8b54d158a25
Tx public key: f8e1f853365e0e04707e7c72a8ba7d21933e1e239a4e591a79882462a86d86c2
Timestamp: 1736717913 Timestamp [UCT]: 2025-01-12 21:38:33 Age [y:d:h:m:s]: 00:095:08:32:00
Block: 1196011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67941 RingCT/type: yes/0
Extra: 01f8e1f853365e0e04707e7c72a8ba7d21933e1e239a4e591a79882462a86d86c20211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67d12d04c906d41ac0a3148707ee510fa4876314415f62e2215b6830592a8248 0.600000000000 1682608 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": 1196021, "vin": [ { "gen": { "height": 1196011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67d12d04c906d41ac0a3148707ee510fa4876314415f62e2215b6830592a8248" } } ], "extra": [ 1, 248, 225, 248, 83, 54, 94, 14, 4, 112, 126, 124, 114, 168, 186, 125, 33, 147, 62, 30, 35, 154, 78, 89, 26, 121, 136, 36, 98, 168, 109, 134, 194, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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