Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cdc8e97def5343e05988a2709370237683f7c5ce337c53f2834386dae22a763

Tx prefix hash: c0ea8a5f2dc23df1c02413e6648154ffe2b107a2fa871b4d793ca938958684df
Tx public key: e5d4418a230834970c511e7a2166f131329457e802f024f35e6ce39127eea44a
Timestamp: 1751797372 Timestamp [UCT]: 2025-07-06 10:22:52 Age [y:d:h:m:s]: 00:137:08:35:28
Block: 1319866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96564 RingCT/type: yes/0
Extra: 01e5d4418a230834970c511e7a2166f131329457e802f024f35e6ce39127eea44a021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13e03d54818dfd4419eae322c7f88b55a4e11d1f726c3aff38cd706060b0d141 0.600000000000 1807559 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": 1319876, "vin": [ { "gen": { "height": 1319866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13e03d54818dfd4419eae322c7f88b55a4e11d1f726c3aff38cd706060b0d141" } } ], "extra": [ 1, 229, 212, 65, 138, 35, 8, 52, 151, 12, 81, 30, 122, 33, 102, 241, 49, 50, 148, 87, 232, 2, 240, 36, 243, 94, 108, 227, 145, 39, 238, 164, 74, 2, 17, 0, 0, 0, 3, 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