Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4dc9a1847ea367df1005b9b884b337d1555539d2ac5f835feaf82e289c0902f

Tx prefix hash: 058c2ca50f1a84c0078765fc9f2cab5915c1caa0db6a4dcc062aa0f4f5aa4adf
Tx public key: 92c877d371b36a9e043ce2792445e99e410cd2744a1c13bedff26a70293c937e
Timestamp: 1756379814 Timestamp [UCT]: 2025-08-28 11:16:54 Age [y:d:h:m:s]: 00:155:10:52:34
Block: 1356239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110937 RingCT/type: yes/0
Extra: 0192c877d371b36a9e043ce2792445e99e410cd2744a1c13bedff26a70293c937e0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd5617d3f2370061ce04d3d72c3642867899b1d0a25b12fba7edd8d30974c07b 0.600000000000 1844246 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": 1356249, "vin": [ { "gen": { "height": 1356239 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd5617d3f2370061ce04d3d72c3642867899b1d0a25b12fba7edd8d30974c07b" } } ], "extra": [ 1, 146, 200, 119, 211, 113, 179, 106, 158, 4, 60, 226, 121, 36, 69, 233, 158, 65, 12, 210, 116, 74, 28, 19, 190, 223, 242, 106, 112, 41, 60, 147, 126, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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