Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c30ff30aa62317eae6922506ae6cba4b8d08c645d0287bef3dc45786a38dcc5

Tx prefix hash: b915a106aa56a4196483e71eaf0f3546487414f5c5036f0d2e39cc5aeb47cb4c
Tx public key: cbe58fe06126ad2a0fea7482ea8380194774eecc995934df5ede337d08de1b72
Timestamp: 1758256691 Timestamp [UCT]: 2025-09-19 04:38:11 Age [y:d:h:m:s]: 00:106:03:41:16
Block: 1371617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76007 RingCT/type: yes/0
Extra: 01cbe58fe06126ad2a0fea7482ea8380194774eecc995934df5ede337d08de1b72021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c7fdd2effb0d4a4bb934f0aac41b25b97e44c912e3b2f38f62d476c08e2c521 0.600000000000 1859694 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": 1371627, "vin": [ { "gen": { "height": 1371617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c7fdd2effb0d4a4bb934f0aac41b25b97e44c912e3b2f38f62d476c08e2c521" } } ], "extra": [ 1, 203, 229, 143, 224, 97, 38, 173, 42, 15, 234, 116, 130, 234, 131, 128, 25, 71, 116, 238, 204, 153, 89, 52, 223, 94, 222, 51, 125, 8, 222, 27, 114, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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