Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 179a9cc5df84c4556b8cd950d093997c7d98908f570da154cba0ca49038d1263

Tx prefix hash: 4f5b3565c9c5f66fea6a8d853477236c29a69a45ff1853362acbeb40b931ce59
Tx public key: 146c1f4578e16b4174cd5f4112c6a81dfb7b240c213523370316b1f509e15bf8
Timestamp: 1745148365 Timestamp [UCT]: 2025-04-20 11:26:05 Age [y:d:h:m:s]: 00:044:18:36:28
Block: 1265533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32047 RingCT/type: yes/0
Extra: 01146c1f4578e16b4174cd5f4112c6a81dfb7b240c213523370316b1f509e15bf802110000000ddbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac6aeea72271d00922f50f7529e918e968bc8fa2e1d0567f9c414b68f258c983 0.600000000000 1752744 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": 1265543, "vin": [ { "gen": { "height": 1265533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac6aeea72271d00922f50f7529e918e968bc8fa2e1d0567f9c414b68f258c983" } } ], "extra": [ 1, 20, 108, 31, 69, 120, 225, 107, 65, 116, 205, 95, 65, 18, 198, 168, 29, 251, 123, 36, 12, 33, 53, 35, 55, 3, 22, 177, 245, 9, 225, 91, 248, 2, 17, 0, 0, 0, 13, 219, 181, 113, 193, 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