Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3483fed9c003348442a1d6573239c87a9eff60f0afb1838e72724d10f9593308

Tx prefix hash: 2bd1c94fd17ee256a355c5c394f3507419ae04f74032262def902c7a7afa348c
Tx public key: a8c4b3dc08d3b37726270bf739ee051769cef5a09e5e4ed31b294aadb6a3d364
Timestamp: 1705275317 Timestamp [UCT]: 2024-01-14 23:35:17 Age [y:d:h:m:s]: 01:063:16:04:55
Block: 935457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306622 RingCT/type: yes/0
Extra: 01a8c4b3dc08d3b37726270bf739ee051769cef5a09e5e4ed31b294aadb6a3d3640211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5386c4922a54d8392fbe9d7dcb5af465ff7449ad12bf6a7581f635178b4b125f 0.600000000000 1393473 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": 935467, "vin": [ { "gen": { "height": 935457 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5386c4922a54d8392fbe9d7dcb5af465ff7449ad12bf6a7581f635178b4b125f" } } ], "extra": [ 1, 168, 196, 179, 220, 8, 211, 179, 119, 38, 39, 11, 247, 57, 238, 5, 23, 105, 206, 245, 160, 158, 94, 78, 211, 27, 41, 74, 173, 182, 163, 211, 100, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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