Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6e3d41f07434eac55c2ae9d708ed952ee8433d6f510217053195f9b0aafdbb0

Tx prefix hash: 65f52cd6c5e1c445c0560e8c546123288a7419cb44372d8dd0d4f6c470aa5a80
Tx public key: fb037e6ad0423c1711a6cf810a3cc975588bd30cf1a495dd38cee8cdd9af4f7c
Timestamp: 1747255619 Timestamp [UCT]: 2025-05-14 20:46:59 Age [y:d:h:m:s]: 00:146:08:23:39
Block: 1282993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102226 RingCT/type: yes/0
Extra: 01fb037e6ad0423c1711a6cf810a3cc975588bd30cf1a495dd38cee8cdd9af4f7c02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acc89487497f5ec93e3adc4f72227e90673e7c999a979b03562328e711fa3026 0.600000000000 1770408 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": 1283003, "vin": [ { "gen": { "height": 1282993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acc89487497f5ec93e3adc4f72227e90673e7c999a979b03562328e711fa3026" } } ], "extra": [ 1, 251, 3, 126, 106, 208, 66, 60, 23, 17, 166, 207, 129, 10, 60, 201, 117, 88, 139, 211, 12, 241, 164, 149, 221, 56, 206, 232, 205, 217, 175, 79, 124, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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